-
Notifications
You must be signed in to change notification settings - Fork 1.8k
CNV-58930: Correct the links to MTV docs #91493
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@jhradilek: This pull request references CNV-58930 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.19.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
/label cnv |
🤖 Wed Apr 02 16:22:22 - Prow CI generated the docs preview: |
@jhradilek: This pull request references CNV-58930 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.19.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
The Migration Toolkit for Virtualization documentation has been significantly improved since the time I wrote this procedure and has dedicated chapters for each source provider. These chapters are well organized and do a great job at outlining the migration process. I therefore do not think it is desirable to duplicate this content in the CNV docs.
349592b
to
f19456a
Compare
@jhradilek: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
/label peer-review-needed |
/lgtm I would recommend a QE review before merging/merge review. |
Thank you. Not sure QE review is needed considering I am offloading a lot of the previously QE reviewed information on MTV docs, and all I am adding are links to a reviewed content. |
/label merge-review-needed |
Hi @jhradilek . I do not see a QE ack on this PR. Would you be OK to get one? Just more for the version change. |
Hi @dfitzmau, thank you, working on getting it. |
/lgtm |
Thank you, Leon! @dfitzmau QE has reviewed the pull request, we should be all set to merge. |
/cherrypick enterprise-4.19 |
/cherrypick enterprise-4.18 |
/cherrypick enterprise-4.17 |
@dfitzmau: new pull request created: #91858 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@dfitzmau: new pull request created: #91859 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@dfitzmau: new pull request created: #91860 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Version(s): 4.17+
Issue: CNV-58930
Link to docs preview:
QE review:
Additional information:
The Migration Toolkit for Virtualization documentation has been significantly improved since the time I wrote this procedure and has dedicated chapters for each source provider. These chapters are well organized and do a great job at outlining the migration process. I therefore do not think it is desirable to duplicate this content in the CNV docs.